Arm backend: Output pytest report in trunk jobs#19555
Conversation
When a pytest report is output to $RUNNER_TEST_RESULTS_DIR, the linux_job_v2.yml workflow can pick it up and surface it in github ci. Signed-off-by: Erik Lundell <erik.lundell@arm.com> Change-Id: Ief15f8cbf6c135e6823078d620f7b7f46615cdf3
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19555
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 3 New Failures, 1 Cancelled Job, 7 Unrelated FailuresAs of commit 448c268 with merge base f1062a7 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOB - The following job was cancelled. Please retry:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following jobs failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
When a pytest report is output to $RUNNER_TEST_RESULTS_DIR, the linux_job_v2.yml workflow can pick it up and
surface it in github ci.
cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani